Skip to content

Conversation

@smarterclayton
Copy link
Contributor

@smarterclayton smarterclayton commented Jan 15, 2020

Installer was failing, the grep caused setup to be "successful", and the test container then immediately failed.

Fallout from yesterday's #6692, started failing about 23 hours ago

Installer was failing, the grep caused setup to be "successful", and
the test container then immediately failed.
@openshift-ci-robot openshift-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jan 15, 2020
@wking
Copy link
Member

wking commented Jan 15, 2020

Fixes the installer exit code being swallowed since #6020

/lgtm

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smarterclayton, wking

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 15, 2020
@openshift-merge-robot openshift-merge-robot merged commit c7a5f4c into openshift:master Jan 15, 2020
@openshift-ci-robot
Copy link
Contributor

@smarterclayton: Updated the following 9 configmaps:

  • prow-job-cluster-launch-installer-src configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-launch-installer-upi-e2e configmap in namespace ci at cluster ci/api-build01-ci-devcluster-openshift-com:6443 using the following files:
    • key cluster-launch-installer-upi-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster ci/api-build01-ci-devcluster-openshift-com:6443 using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-launch-installer-src configmap in namespace ci at cluster ci/api-build01-ci-devcluster-openshift-com:6443 using the following files:
    • key cluster-launch-installer-src.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml
  • prow-job-cluster-launch-installer-upi-e2e configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-installer-upi-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e.yaml
  • prow-job-cluster-launch-installer-upi-e2e configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-installer-upi-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-upi-e2e.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci at cluster default using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
  • prow-job-cluster-launch-installer-e2e configmap in namespace ci-stg at cluster default using the following files:
    • key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
Details

In response to this:

Installer was failing, the grep caused setup to be "successful", and the test container then immediately failed.

Fallout from yesterday's #6692, started failing about 23 hours ago

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-ci-robot
Copy link
Contributor

@smarterclayton: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/rehearse/openshift-cnv/cnv-ci/master/e2e-test 5c6ca8a link /test pj-rehearse
ci/rehearse/openshift/cluster-api-actuator-pkg/master/e2e-azure-operator 5c6ca8a link /test pj-rehearse
ci/rehearse/codeready-toolchain/host-operator/master/e2e 5c6ca8a link /test pj-rehearse
ci/rehearse/openshift/installer/fcos/e2e-vsphere 5c6ca8a link /test pj-rehearse
ci/rehearse/openshift/cloud-credential-operator/master/e2e-gcp 5c6ca8a link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-gcp-upi 5c6ca8a link /test pj-rehearse
ci/rehearse/openshift/installer/master/e2e-aws-proxy 5c6ca8a link /test pj-rehearse
ci/rehearse/openshift/cloud-credential-operator/master/e2e-azure 5c6ca8a link /test pj-rehearse
ci/prow/pj-rehearse 5c6ca8a link /test pj-rehearse

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

bbguimaraes added a commit to bbguimaraes/release that referenced this pull request Jan 16, 2020
openshift#6718 added `set -u` to scripts
that access unset variables.
mandre added a commit to mandre/release that referenced this pull request Jan 16, 2020
Installer was failing, the grep caused setup to be "successful", and
the test container then immediately failed.

Ref openshift#6718
wking added a commit to wking/ci-tools that referenced this pull request Jan 24, 2020
Bringing over a number of changes which have landed in
ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml
as of openshift/release@c64d5d7d8f (Merge pull request #6845 from
wking/shared-subnets-for-other-regions, 2020-01-23).

One series was AWS region sharding:

* openshift/release@b7179335a3
  (ci-operator/templates/openshift/installer/cluster-launch-installer-*:
  Random AWS regions for IPI, 2020-01-23, openshift/release#6833).
* openshift/release@7e38260d25
  (ci-operator/templates/openshift/installer: Shared subnets for new
  regions, 2020-01-23, openshift/release#6845).

Another series was the password removal followed by a bunch of
pipefail fumbling ;)

* openshift/release@4847cb5477 (clean up install log output,
  2020-01-13, openshift/release#6692).
* openshift/release@5c6ca8a506 (templates: Use 'pipefail' so that grep
  doesn't mask install failures, 2020-01-15, openshift/release#6718).
* openshift/release@bee15b9fa8 (add -eou pipefail to remaining job
  templates, 2020-01-16, openshift/release#6738)
* openshift/release@07bd61d677 (Revert "add -eou pipefail to remaining
  job templates", 2020-01-17, openshift/release#6748).
* openshift/release@ca655477ca (Revert "Revert "add -eou pipefail to
  remaining job templates"", 2020-01-17, openshift/release#6750).
* openshift/release@9d7453156b (tolerate undefined env vars in
  teardown, 2020-01-17, openshift/release#6750).

And there was also:

* openshift/release@c6c2efb3fc (templates: Add ipv6 variant that
  triggers azure singlestack, 2020-01-22, openshift/release#6809).
* openshift/release@752455a47f (templates: fix check for unset
  variable, 2020-01-16, openshift/release#6723).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants